Upgrading from vFire 9.2 or Below

This topic describes three methods for upgrading vFire systems on 9.2 or lower.

Newer vFire Setup and Patch packages cannot be applied to web servers configured for 9.2 or below due to incompatible server requirements. Therefore vFire must be installed on a new web server that meets the updated server requirements as detailed in Web Server Requirements.

It is assumed the database is on a separate server to the web server used by vFire, and that the database server is not being migrated as part of this activity.

Select a method

Select the method that best suits the business needs of the organization, taking into consideration how many web servers or VMs are available, and whether or not you want legacy folder structures, files, and registry keys on the new server.

Method As described on Complexity Level Legacy Items Multiple Servers Available
Method 1 Method 1 Easy Yes No
Method 2 Method 2 Easy No Yes
Method 3 Method 3 Very complex No No

Method 1

Use this method if:

  • There are only two servers available: the old server, and the new server the system is being migrated to.
  • You do not mind legacy registry keys, folder structures, and files on the new server.
  • Legacy items are harmless but redundant, and consume space unnecessarily.

Before you begin

Ensure the new server meetings the Prerequisites.

Download the vFire Core Setup package that matches the version of the system on the old server.

Download the vFire Core Patch package for the version you wish to upgrade to.

On the new web server the system is migrating to

  1. Install vFire by running the Setup package that matches the version of the system on the old server.

  2. After vFire installation is complete, create a new vFire system using the System Setup Wizard in the vFire Server Console.

    • At the Database step, enter the existing database details.

    • If prompted to upgrade the database, select NO.

    • Complete the steps in the System Setup Wizard.
  3. Log into the new system and ensure it works before continuing

  4. Install the Patch package of the version you wish to upgrade to.

  5. Press Run on the Patch Tool, which launches automatically when InstallShield Wizard completes.

    • If prompted to upgrade the database, select YES.
  6. When the Patch Tool completes, the system is ready to be used.

  7. Once system links have been redirected to the new server, the old server can be decommissioned. If this is not immediately possible, ensure the vFire Services are Stopped and set to Manual on the old server to prevent conflicts.

Method 2

Use this method if:

  • There are three servers available: the old server, a temporary server, and the new server the system is being migrated to.
  • You prefer not to have legacy registry keys, folder structures, and files on the new server.

Before you begin

Ensure the temporary server, and new permanent server, both meeting the Prerequisites.

Download the vFire Core Setup package that matches the version of the system on the old server.

Download the vFire Core Patch package for the version you wish to upgrade to.

On the temporary web server

  1. Install vFire by running the Setup package that matches the version of the system on the old server.
  2. After vFire installation is complete, create a new vFire system using the System Setup Wizard in the vFire Server Console.
    • At the Database step, enter the existing database details.
    • If prompted to upgrade the database, select NO.
    • Complete the steps in the System Setup Wizard.
  3. Log into the new system and ensure it works before continuing.

  4. Install the Patch package of the version you wish to upgrade to.
  5. Press Run on the Patch Tool, which launches automatically when InstallShield Wizard completes.
    • If prompted to upgrade the database, select YES.

On the new web server the system is migrating to

  1. Install vFire by running the Setup package for the version you wish to upgrade to.
  2. After vFire installation is complete, create a new vFire system using the System Setup Wizard in the vFire Server Console.
    • At the Database step, enter the existing database details.
    • If prompted to upgrade the database, select NO.
    • Complete the steps in the System Setup Wizard.
  3. When the Patch Tool completes, the system is ready to be used.

Decommission the unneeded web servers

Uninstall vFire from the temporary web server once vFire is ready for use on the new server. Or, decommission the server. If this is not immediately possible, ensure the vFire Services are Stopped and set to Manual.

  • Once system links have been redirected to the new server, the old server can be decommissioned. If this is not immediately possible, ensure the vFire Services are Stopped and set to Manual on the old server to prevent conflicts.
  • Method 3

    This method should not be used without assistance from Alemba Professional Services.

    Use this method if:

    • There are only two servers available: the old server, and the new server the system is being migrated to.
    • You prefer not to have legacy registry keys, folder structures, and files on the new server.

    Before you begin

    Ensure the new server meetings the Prerequisites.

    Download the vFire Core Setup package that is one version lower than the version you wish to upgrade to.

    Download the vFire Core Patch package for the version you wish to upgrade to.

    Create a blank database on the database server.

     

    On the new web server the system is migrating to

    1. Install vFire by running the Setup package of the version lower than the you wish to upgrade to.

      If you want to upgrade to 9.7, install 9.6 at this step.

    2. After vFire installation is complete, create a new vFire system using the System Setup Wizard in the vFire Server Console.
      • At the Database step, enter details of a new blank database (which should have been already created on the database server).
      • If prompted to upgrade the database, select NO.
      • Complete the steps in the System Setup Wizard.
    3. Update the database details for the newly created system:
      • In the Server Console, select the newly created system and select Properties.
      • Select the Database tab and enter details for the database used by the system you are planning to upgrade.
      • Save the system properties and exit the Server Console.
    4. Navigate to the directory where vFire is installed and update files as follows:
      • Overwrite the files in the Original directory with the files from vFire on the old web server.
      • Copy files from the Original directory on the old server: C:\Program Files (x86)\VMware\Service Manager\Original
        Past files into the Original directory on the new server: C:\Program Files\Alemba\vFire\Original

      • Overwrite the files in the system directory with the files from vFire on the old web server.
      • Copy files from the system directory on the old server: C:\Program Files (x86)\VMware\Service Manager\System1
        Past files into the system directory on the new server: C:\Program Files\Alemba\vFire\System1

    5. Update the vFire registry keys:
      • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Alemba\vFireCore
      • Find string Version and change the value to the version of your existing system.
      • Change 9.7.1 to 9.1.9 (where 9.7.1 is the vFire version installed on the new server, and 9.1.9 is the version of vFire on the old server).

    6. Install the Patch package of the version you wish to upgrade to.
    7. Press Run on the Patch Tool, which launches automatically when InstallShield Wizard completes.
      • If prompted to upgrade the database, select YES.
    8. Navigate to the directory where vFire is installed copy files from the Original directory to the system directory.
    9. Only perform this step if standard system files were customized. This reverts all files to default.

      Copy files from the Original directory on the new server: C:\Program Files\Alemba\vFire\Original
      Paste files into the system directory on the new server: C:\Program Files\Alemba\vFire\System

       
    10. The new system is ready to be used.
    11. Once system links have been redirected to the new server, the old server can be decommissioned. If this is not immediately possible, ensure the vFire Services are Stopped and set to Manual on the old server to prevent conflicts.